Skip to content

Conversation

AnatoliB
Copy link
Owner

@AnatoliB AnatoliB commented Sep 16, 2025

This telemetry depends on the fact that console output lines starting with a special prefix are recognized by the Functions Host and forwarded to internal Functions telemetry destinations.

@AnatoliB AnatoliB marked this pull request as ready for review September 16, 2025 16:58
activity_name: str,
):
"""Adapts the synchronous OpenAI Agents function to an Durable orchestrator generator."""
# Log versions the first time this generator is invoked
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's fine to enable by default, but we should add a means to disable the logging.

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@philliphoff Let me clarify though: this data will be propagated to internal Functions telemetry only for apps that are actually deployed to the public Azure Functions service. For these apps, there is already quite a lot of data collected without the customer having any opportunity to opt out (e.g. module usage stats, feature usage stats, and even specific app configurations). I don't feel we have enough reason to make an exception in this case.

For apps running locally or hosted on customer's own infrastructure, these logs will not be collected by the Azure Functions service in any case.

@AnatoliB AnatoliB merged commit fac5708 into durable-openai-agent Sep 18, 2025
4 checks passed
@AnatoliB AnatoliB deleted the anatolib/usage-telemetry branch September 18, 2025 05:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants